home *** CD-ROM | disk | FTP | other *** search
Text File | 1990-06-01 | 1.2 KB | 34 lines | [TEXT/GEOL] |
- Item forwarded by LOOMIS to GUITTET1
-
- Item 4308314 30-May-90 06:30PDT
-
- From: V0683 Amoco Tech, Eric Berdahl,VAR
-
- To: MACAPP.TECH$ MacApp Technical
-
- Sub: UAevtDialog anyone?
-
- Here’s a nutty thought:
-
- How ’bout a set of classes (say, UAevtDialog) that look and act just like the
- UDialog classes that we all know and love, but that send AppleEvents to a
- specified process (say, gAevtProcess). Let me explicate some more.
-
- gAevtProcess defaults to the current application (set in IApplication) but can
- be reset by the user to any other valid process (valid here is purposefully
- ambiguous). TAevtButtons could send action AppleEvents (or dismiss dialogs,
- etc). TAevtScrollBars could send set property AppleEvents.
-
- Why would anyone want to do this? Consider an application which is completely
- AppleEvent aware but has a UI that isn’t great. Using this mechanism, you can
- write a better UI for the fantastic programming engine that someone else has
- written.
-
- What do the masses think?
-
- Donning my asbestos suit (just in case),
- Eric Berdahl
- Amoco Technology Company
- AppleLink: V0683
-
-